Package | hl7.ehrs.ehrsfmr21 |
Type | Requirements |
Id | Id |
FHIR Version | R5 |
Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-TI.2.1.1.html |
Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI.2.1.1 |
Version | 2.1.0 |
Status | active |
Date | 2024-11-26T16:30:50+00:00 |
Name | TI_2_1_1_Record_Entry_Audit_Triggers |
Title | TI.2.1.1 Record Entry Audit Triggers (Function) |
Experimental | False |
Realm | uv |
Authority | hl7 |
Description | Manage Record Entry Audit Triggers |
Purpose | Record Entries are managed throughout their lifespan at various points in their lifecycle. Record Entry Audit Triggers are designed to capture Record Entry related events including key metadata (who, what, when, where, why). See Function [[RI.1]], Record Lifecycle. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Manage Record Entry Audit Triggers
Record Entries are managed throughout their lifespan at various points in their lifecycle. Record Entry Audit Triggers are designed to capture Record Entry related events including key metadata (who, what, when, where, why). See Function [[RI.1]], Record Lifecycle.
TI.2.1.1#01 | SHALL |
The system SHALL conform to function [[RI.1]] (Record Lifecycle) and its RI.1.x.1 Subsections to capture and maintain Record Entry Audit Metadata. |
TI.2.1.1#02 | dependent SHALL |
The system SHALL link an Audit Log Entry to each Record Entry according to scope of practice, organizational policy, and/or jurisdictional law. |
TI.2.1.1#03 | SHALL |
The system SHALL harmonize Audit Log Entry Metadata and corresponding Record Entry Metadata to ensure they remain identical. |
{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-TI.2.1.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Manage Record Entry Audit Triggers</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Record Entries are managed throughout their lifespan at various points in their lifecycle. Record Entry Audit Triggers are designed to capture Record Entry related events including key metadata (who, what, when, where, why). See Function [[RI.1]], Record Lifecycle.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.2.1.1#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL conform to function [[RI.1]] (Record Lifecycle) and its RI.1.x.1 Subsections to capture and maintain Record Entry Audit Metadata.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.2.1.1#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL link an Audit Log Entry to each Record Entry according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>TI.2.1.1#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL harmonize Audit Log Entry Metadata and corresponding Record Entry Metadata to ensure they remain identical.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-TI.2.1.1",
"version" : "2.1.0",
"name" : "TI_2_1_1_Record_Entry_Audit_Triggers",
"title" : "TI.2.1.1 Record Entry Audit Triggers (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Manage Record Entry Audit Triggers",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Record Entries are managed throughout their lifespan at various points in their lifecycle. Record Entry Audit Triggers are designed to capture Record Entry related events including key metadata (who, what, when, where, why). See Function [[RI.1]], Record Lifecycle.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-TI.2.1.1-01",
"label" : "TI.2.1.1#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL conform to function [[RI.1]] (Record Lifecycle) and its RI.1.x.1 Subsections to capture and maintain Record Entry Audit Metadata."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-TI.2.1.1-02",
"label" : "TI.2.1.1#02",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL link an Audit Log Entry to each Record Entry according to scope of practice, organizational policy, and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-TI.2.1.1-03",
"label" : "TI.2.1.1#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL harmonize Audit Log Entry Metadata and corresponding Record Entry Metadata to ensure they remain identical."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.